Methods, systems and media players for rendering different media types

ABSTRACT

Methods and systems are described that assist media players in rendering different media types. In some embodiments, a unified rendering area is provided and managed such that multiple different media types are rendered by the media player in the same user interface area. This unified rendering area thus permits different media types to be presented to a user in an integrated and organized manner. An underlying object model promotes the unified rendering area by providing a base rendering object that has properties that are shared among the different media types. Object sub-classes are provided and are each associated with a different media type, and have properties that extend the shared properties of the base rendering object. In addition, an inventive approach to visualizations is presented that provides better synchronization between a visualization and its associated audio stream.

TECHNICAL FIELD

This invention relates to methods, systems and media players forrendering different media types.

BACKGROUND

Today, individuals are able to use their computers to download and playvarious media content. For example, many companies offer so-called mediaplayers that reside on a computer and allow a user to download andexperience a variety of media content. For example, users can downloadmedia files associated with music and listen to the music via theirmedia player. Users can also download video data and animation data andview these using their media players.

One problem associated with prior art media players is they all tend todisplay different types of media in different ways. For example, somemedia players are configured to provide a “visualization” when they playaudio files. A visualization is typically a piece of software that“reacts” to the audio that is being played by providing a generallychanging, often artistic visual display for the user to enjoy.Visualizations are often presented, by the prior art media players, in awindow that is different from the media player window or on a differentportion of the user's display. This causes the user to shift their focusaway from the media player and to the newly displayed window. In asimilar manner, video data or video streams are often provided withinyet another different window which is either an entirely new displaywindow to which the user is “flipped”, or is a window located on adifferent portion of the user's display. Accordingly, these differentwindows in different portions of the user's display all combine for afairly disparate and unorganized user experience. It is always desirableto improve the user's experience.

In addition, there are problems associated with prior artvisualizations. As an example, consider the following. One of the thingsthat makes visualizations enjoyable and interesting for users is theextent to which they “mirror” or follow the audio being played on themedia player. Past visualization technology has led to visualizationsthat do not mirror or follow the audio as closely as one would like.This leads to things such as a lag in what the user sees after they haveheard a particular piece of audio. It would be desirable to improve uponthis media player feature.

Accordingly, this invention arose out of concerns associated withproviding improved media players and user experiences regarding thesame.

SUMMARY

Methods and systems are described that assist media players in renderingdifferent media types. In some embodiments, a unified rendering area isprovided and managed such that multiple different media types arerendered by the media player in the same user interface area. Thisunified rendering area thus permits different media types to bepresented to a user in an integrated and organized manner. An underlyingobject model promotes the unified rendering area by providing a baserendering object that has properties that are shared among the differentmedia types. Object sub-classes are provided and are each associatedwith a different media type, and have properties that extend the sharedproperties of the base rendering object. In addition, an inventiveapproach to visualizations is presented that provides bettersynchronization between a visualization and its associated audio stream.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is block diagram of a system in which various embodiments can beimplemented.

FIG. 2 is a block diagram of an exemplary server computer.

FIG. 3 is a block diagram of an exemplary client computer.

FIG. 4 is a diagram of an exemplary media player user interface (UI)that can be provided in accordance with one embodiment. The UIillustrates a unified rendering area in accordance with one embodiment.

FIG. 5 is a flow diagram that describes steps in a method in accordancewith one embodiment.

FIG. 6 is a block diagram that helps to illustrate an object model inaccordance with one embodiment.

FIG. 7 is a flow diagram that describes steps in a method in accordancewith one embodiment.

FIG. 8 is a block diagram that illustrates an exemplary system forsynchronizing a visualization with audio samples in accordance with oneembodiment.

FIG. 9 is a block diagram that illustrates exemplary components of asample pre-processor in accordance with one embodiment.

FIG. 10 is a flow diagram that describes steps in a method in accordancewith one embodiment.

FIG. 11 is a flow diagram that describes steps in a method in accordancewith one embodiment.

FIG. 12 is a flow diagram that describes steps in a method in accordancewith one embodiment.

FIG. 13 is a timeline that is useful in understanding aspects of oneembodiment.

FIG. 14 is a timeline that is useful in understanding aspects of oneembodiment.

FIG. 15 is a timeline that is useful in understanding aspects of oneembodiment.

DETAILED DESCRIPTION

Overview

Methods and systems are described that assist media players in renderingdifferent media types. In some embodiments, a unified rendering area isprovided and managed such that multiple different media types arerendered by the media player in the same user interface area. Thisunified rendering area thus permits different media types to bepresented to a user in an integrated and organized manner. An underlyingobject model promotes the unified rendering area by providing a baserendering object that has properties that are shared among the differentmedia types. Object sub-classes are provided and are each associatedwith a different media type, and have properties that extend the sharedproperties of the base rendering object. In addition, an inventiveapproach to visualizations is presented that provides bettersynchronization between a visualization and its associated audio stream.

Exemplary System

FIG. 1 shows exemplary systems and a network, generally at 100, in whichthe described embodiments can be implemented. The systems can beimplemented in connection with any suitable network. In the embodimentshown, the system can be implemented over the public Internet, using theWorld Wide Web (WWW or Web), and its hyperlinking capabilities. Thedescription herein assumes a general knowledge of technologies relatingto the Internet, and specifically of topics relating to filespecification, file retrieval, streaming multimedia content, andhyperlinking technology.

System 100 includes one or more clients 102 and one or more networkservers 104, all of which are connected for data communications over theInternet 106. Each client and server can be implemented as a personalcomputer or a similar computer of the type that is typically referred toas “IBM-compatible.”

An example of a server computer 104 is illustrated in block form in FIG.2 and includes conventional components such as a data processor 200;volatile and non-volatile primary electronic memory 202; secondarymemory 204 such as hard disks and floppy disks or other removable media;network interface components 206; display devices interfaces and drivers208; and other components that are well known. The computer runs anoperating system 210 such as the Windows NT operating system. The servercan also be configured with a digital rights management module 212 thatis programmed to provide and enforce digital rights with respect tomultimedia and other content that it sends to clients 102. Such digitalrights can include, without limitation, functionalities includingencryption, key exchange, license delivery and the like.

Network servers 104 and their operating systems can be configured inaccordance with known technology, so that they are capable of streamingdata connections with clients. The servers include storage components(such as secondary memory 204), on which various data files are storedand formatted appropriately for efficient transmission using knownprotocols. Compression techniques can be desirably used to make the mostefficient use of limited Internet bandwidth.

FIG. 3 shows an example of a client computer 102. Various types ofclients can be utilized, such as personal computers, palmtop computers,notebook computers, personal organizers, etc. Client computer 104includes conventional components similar to those of network server 104,including a data processor 300; volatile and non-volatile primaryelectronic memory 301; secondary memory 302 such as hard disks andfloppy disks or other removable media; network interface components 303;display devices interfaces and drivers 304; audio recording andrendering components 305; and other components as are common in personalcomputers.

In the case of both network server 104 and client computer 102, the dataprocessors are programmed by means of instructions stored at differenttimes in the various computer-readable storage media of the computers.Programs are typically distributed, for example, on floppy disks orCD-ROMs. From there, they are installed or loaded into the secondarymemory of a computer. At execution, they are loaded at least partiallyinto the computer's primary electronic memory. The embodiments describedherein can include these various types of computer-readable storagemedia when such media contain instructions or programs for implementingthe described steps in conjunction with a microprocessor or other dataprocessor. The embodiments can also include the computer itself whenprogrammed according to the methods and techniques described below.

For purposes of illustration, programs and program components are shownin FIGS. 2 and 3 as discrete blocks within a computer, although it isrecognized that such programs and components reside at various times indifferent storage components of the computer.

Client 102 is desirably configured with a consumer-oriented operatingsystem 306, such as one of Microsoft Corporation's Windows operatingsystems. In addition, client 102 can run an Internet browser 307, suchas Microsoft's Internet Explorer.

Client 102 can also include a multimedia data player or renderingcomponent 308. An exemplary multimedia player is Microsoft's MediaPlayer 7. This software component can be capable of establishing dataconnections with Internet servers or other servers, and of rendering themultimedia data as audio, video, visualizations, text, HTML and thelike.

Player 308 can be implemented in any suitable hardware, software,firmware, or combination thereof. In the illustrated and describedembodiment, it can be implemented as a standalone software component, asan ActiveX control (ActiveX controls are standard features of programsdesigned for Windows operating systems), or any other suitable softwarecomponent.

In the illustrated and described embodiment, media player 308 isregistered with the operating system so that it is invoked to opencertain types of files in response to user requests. In the Windowsoperating system, such a user request can be made by clicking on an iconor a link that is associated with the file types. For example, whenbrowsing to a Web site that contains links to certain music forpurchasing, a user can simply click on a link. When this happens, themedia player can be loaded and executed, and the file types can beprovided to the media player for processing that is described below inmore detail.

Exemplary Media Player UI

FIG. 4 shows one exemplary media player user interface (UI) 400 thatcomprises part of a media player. The media player UI includes a menu402 that can be used to manage the media player and various mediacontent that can be played on and by the media player. Drop down menusare provided for file management, view management, play management,tools management and help management. In addition, a set of controls 404are provided that enable a user to pause, stop, rewind, fast forward andadjust the volume of media that is currently playing on the mediaplayer.

A rendering area or pane 406 is provided in the UI and serves to enablemultiple different types of media to be consumed and displayed for theuser. The rendering area is highlighted with dashed lines. In theillustrated example, the U2 song “Beautiful Day” is playing and isaccompanied by some visually pleasing art as well as informationconcerning the track. In one embodiment, all media types that arecapable of being consumed by the media player are rendered in the samerendering area. These media types include, without limitation, audio,video, skins, borders, text, HTML and the like. Skins are discussed inmore detail in U.S. patent applications Ser. Nos. 09/773,446 and09/773,457, the disclosures of which are incorporated by reference.

Having a unified rendering area provides an organized and integrateduser experience and overcomes problems associated with prior art mediaplayers discussed in the “Background” section above.

FIG. 5 is a flow diagram that describes steps in a method of providing auser interface in accordance with one embodiment. The method can beimplemented in any suitable hardware, software, firmware or combinationthereof. In the described embodiment, the method is implemented insoftware.

Step 500 provides a media player user interface. This step isimplemented in software code that presents a user interface to the userwhen a media player application is loaded and executed. Step 502provides a unified rendering area in the media player user interface.This unified rendering area is provided for rendering different mediatypes for the user. It provides one common area in which the differentmedia types can be rendered. In one embodiment, all visual media typesthat are capable of being rendered by the media player are rendered inthis area. Step 504 then renders one or more different media types inthe unified rendering area.

Although the method of FIG. 5 can be implemented in any suitablesoftware using any suitable software programming techniques, theillustrated and described method is implemented using a common runtimemodel that unifies multiple (or all) media type rendering under onecommon rendering paradigm. In this model, there are different componentsthat render the media associated with the different media types. Themedia player application, however, hosts all of the different componentsin the same area. From a user's perspective, then, all of the differenttypes of media are rendered in the same area.

Exemplary Object Model

FIG. 6 shows components of an exemplary object model in accordance withone embodiment generally at 600. Object model 600 enables differentmedia types to be rendered in the same rendering area on a media playerUI. The object model has shared attributes that all objects support.Individual media type objects have their own special attributes thatthey support. Examples of these attributes are given below.

The object model includes a base object called a “rendering object” 602.Rendering object 602 manages and defines the unified rendering area 406(FIG. 4) where all of the different media types are rendered. Inaddition to rendering object 602, there are multiple different mediatype rendering objects that are associated with the different mediatypes that can get rendered the unified rendering area. In theillustrated and described embodiment, these other rendering objectsinclude, without limitation, a skin rendering object 604, a videorendering object 606, an audio rendering object 608, an animationrendering object 610, and an HTML rendering object 612. It should benoted that some media type rendering objects can themselves host arendering object. For example, skin rendering object 604 can host arendering object within it such that other media types can be renderedwithin the skin. For example, a skin can host a video rendering objectso that video can be rendered within a skin. It is to be appreciated andunderstood that other rendering objects associated with other mediatypes can be provided.

Rendering objects 604-612 are subclasses of the base object 602.Essentially then, in this model, rendering object 602 defines theunified rendering area and each of the individual rendering objects604-612 define what actually gets rendered in this area. For example,below each of objects 606, 608, and 610 is a media player skin 614having a unified rendering area 406. As can be seen, video renderingobject 606 causes video data to be rendered in this area; audiorendering object 608 causes a visualization to be rendered in this area;and animation rendering object 610 causes text to be rendered in thisarea. All of these different types of media are rendered in the samelocation.

In this model, the media player application can be unaware of thespecific media type rendering objects (i.e. objects 604-612) and canknow only about the base object 602. When the media player applicationreceives a media type for rendering, it calls the rendering object 602with the particular type of media. The rendering object ascertains theparticular type of media and then calls the appropriate media typerendering object and instructs the object to render the media in theunified rendering area managed by rendering object 602. As an example,consider the following. The media player application receives video datathat is to be rendered by the media player application. The applicationcalls the rendering object 602 and informs it that it has received videodata. Assume also that the rendering object 602 controls a rectanglethat defines the unified rendering area of the UI. The rendering objectascertains the correct media type rendering object to call (here, videorendering object 606 ), call the object 606, and instructs object 606 torender the media in the rectangle (i.e. the unified rendering area)controlled by the rendering object 602. The video rendering object thenrenders the video data in the unified rendering area thus providing a UIexperience that looks like the one shown by skin 614 directly undervideo rendering object 606.

Common Runtime Properties

In the above object model, multiple media types share common runtimeproperties. In the described embodiment, all media types share theseproperties:

Attribute Description clippingColor Specifies or retrieves the color toclip out from the clippingImage bitmap. clippingImage Specifies orretrieves the region to clip the control to. elementType Retrieves thetype of the element (for instance, BUTTON). enabled Specifies orretrieves a value indicating whether the control is enabled or disabled.height Specifies or retrieves the height of the control.horizontalAlignment Specifies or retrieves the horizontal alignment ofthe control when the VIEW or parent SUBVIEW is resized. id Specifies orretrieves the identifier of a control. Can only be set at design time.left Specifies or retrieves the left coordinate of the control.passThrough Specifies or retrieves a value indicating whether thecontrol will pass all mouse events through to the control under it.tabStop Specifies or retrieves a value indicating whether the controlwill be in the tabbing order. top Specifies or retrieves the topcoordinate of the control. verticalAlignment Specifies or retrieves thevertical alignment of the control when the VIEW or parent SUBVIEW isresized. visible Specifies or retrieves the visibility of the control.width Specifies or retrieves the width of the control. zIndex Specifiesor retrieves the order in which the control is rendered.

Examples of video-specific settings that extend these properties forvideo media types include:

Attribute Description backgroundColor Specifies or retrieves thebackground color of the Video control. cursor Specifies or retrieves thecursor value that is used when the mouse is over a clickable area of thevideo. fullScreen Specifies or retrieves a value indicating whether thevideo is displayed in full-screen mode. Can only be set at run time.maintainAspectRatio Specifies or retrieves a value indicating whetherthe video will maintain the aspect ratio when trying to fit within thewidth and height defined for the control. shrinkToFit Specifies orretrieves a value indicating whether the video will shrink to the widthand height defined for the Video control. stretchToFit Specifies orretrieves a value indicating whether the video will stretch itself tothe width and height defined for the Video control. toolTip Specifies orretrieves the ToolTip text for the video window. windowless Specifies orretrieves a value indicating whether the Video control will be windowedor windowless; that is, whether the entire rectangle of the control willbe visible at all times or can be clipped. Can only be set at designtime. zoom Specifies the percentage by which to scale the video.

Examples of audio-specific settings that extend these properties foraudio media types include:

Attribute Description allowAll Specifies or retrieves a value indicatingwhether to include all the visualizations in the registry. currentEffectSpecifies or retrieves the current visualization.currentEffectPresetCount Retrieves number of available presets for thecurrent visualization. currentEffectTitle Retrieves the display title ofthe current visualization. currentEffectType Retrieves the registry nameof the current visualization. currentPreset Specifies or retrieves thecurrent preset of the current visualization. currentPresetTitleRetrieves the title of the current preset of the current visualization.effectCanGoFullScreen Retrieves a value indicating whether the currentvisualization can be displayed full-screen.

Exemplary Method

FIG. 7 is a flow diagram that describes steps in a media renderingmethod in accordance with one embodiment. The method can be implementedin any suitable hardware, software, firmware, or combination thereof. Inthe illustrated and described embodiment, the method is implemented insoftware. This software can comprise part of a media player applicationprogram executing on a client computer.

Step 700 provides a base rendering object that defines a unifiedrendering area. The unified rendering area desirably provides an areawithin which different media types can be rendered. These differentmedia types can comprise any media types that are typically rendered orrenderable by a media player. Specific non-limiting examples are givenabove. Step 702 provides multiple media-type rendering objects that aresubclasses of the base rendering objects. These media-type renderingobjects share common properties among them, and have their ownproperties that extend these common properties. In the illustratedexample, each media type rendering object is associated with a differenttype of media. For example, there are media-type rendering objectsassociated with skins, video, audio (i.e. visualizations), animations,and HTML to name just a few. Each media-type rendering object isprogrammed to render its associated media type. Some media typerendering objects can also host other rendering objects so that themedia associated with the hosted rendering object can be rendered insidea UI provided by the host.

Step 704 receives a media type for rendering. This step can be performedby a media player application. The media type can be received from astreaming source such as over a network, or can comprise a media filethat is retrieved, for example, off of the client hard drive. Once themedia type is received, step 706 ascertains an associated media typerendering object. In the illustrated example, this step can beimplemented by having the media player application call the baserendering object with the media type, whereupon the base renderingobject can ascertain the associated media type rendering object. Step708 then calls the associated media-type rendering object and step 710instructs the media-type rendering object to render media in the unifiedrendering area. In the illustrated and described embodiment, these stepsare implemented by the base rendering object. Step 712 then renders themedia type in the unified rendering area using the media type renderingobject.

The above-describe object model and method permit multiple differentmedia types to be associated with a common rendering area inside ofwhich all associated media can be rendered. The user interface that isprovided by the object model can overcome problems associated with priorart user interfaces by presenting a unified, organized and highlyintegrated user experience regardless of the type of media that is beingrendered.

Visualizations

As noted above, particularly with respect to FIG. 6 and the associateddescription, one aspect of the media player provides so-called“visualizations.” In the FIG. 6 example, visualizations are provided, atleast in part, by the audio rendering object 608, also referred toherein as the “VisHost.” The embodiments described below accuratelysynchronize a visual representation (i.e. visualization) with an audiowaveform that is currently playing on a client computer's speaker.

FIG. 8 shows one embodiment of a system configured to accuratelysynchronize a visual representation with an audio waveform generally at800. System 800 comprises one or more audio sources 802 that provide theaudio waveform. The audio sources provide the audio waveform in the formof samples. Any suitable audio source can be employed such as astreaming source or an audio file. In addition, different types of audiosamples can be provided from relatively simple 8-bit samples, tosomewhat more complex 16-bit samples and the like.

An audio sample preprocessor 804 is provided and performs some differentfunctions. An exemplary audio sample preprocessor is shown in moredetail in FIG. 9.

Referring both to FIGS. 8 and 9, as the audio samples stream into thepreprocessor 804, it builds and maintains a collection of datastructures indicated generally at 806. Each audio sample that is to beplayed by the media player has an associated data structure thatcontains data that characterizes the audio sample. These data structuresare indicated at 806 a, 806 b, and 806 c. The characterizing data islater used to render a visualization that is synchronized with the audiosample when the audio sample is rendered. The preprocessor comprises atimestamp module 900 (FIG. 9) that provides a timestamp for each audiosample. The timestamps for each audio sample are maintained in asample's data structure (FIG. 9). The timestamp is assigned by thetimestamp module to the audio sample based on when the audio sample iscalculated to be rendered by the media player. As an aside, timestampsare assigned based on the current rendering time and a consideration ofhow many additional samples are in the pipeline scheduled for playing.Based on these parameters, a timestamp can be assigned by the timestampmodule.

Preprocessor 804 also preprocesses each audio sample to providecharacterizing data that is to be subsequently used to create avisualization that is associated with each audio sample. In oneembodiment, the preprocessor 804 comprises a spectrum analyzer module902 (FIG. 9) that uses a Fast Fourier Transform (FFT) to convert theaudio samples from the time domain to the frequency domain. The FFTbreaks the audio samples down into a set of 1024 frequency values or, astermed in this document, “frequency data.” The frequency data for eachaudio sample is then maintained in the audio sample's data structure. Inaddition to maintaining the frequency data, the preprocessor 804 caninclude a waveform analysis module 904 that analyzes the audio sample toprovide waveform data. The preprocessor 804 can also includes a streamstate module 906 that provides data associated with the state of theaudio stream (i.e. paused, stopped, playing, and the like).

Referring specifically to FIG. 8, a buffer 808 can be provided to bufferthe audio samples in a manner that will be known and appreciated bythose of skill in the art. A renderer 810 is provided and represents thecomponent or components that are responsible for actually rendering theaudio samples. The renderer can include software as well as hardware,i.e. an audio card.

FIG. 8 also shows audio rendering object or VisHost 608. Associated withthe audio rendering object are various so-called effects. In theillustrated example, the effects include a dot plane effect, a bareffect, and a ambience effect. The effects are essentially software codethat plugs into the audio rendering object 608. Typically, such effectscan be provided by third parties that can program various creativevisualizations. The effects are responsible for creating a visualizationin the unified rendering area 406.

In the illustrated and described embodiment, the audio rendering objectoperates in the following way to ensure that any visualizations that arerendered in unified rendering area 406 are synchronized to the audiosample that is currently being rendered by renderer 810. The audiorendering object has an associated target frame rate that essentiallydefines how frequently the unified rendering area is drawn, redrawn orpainted. As an example, a target frame rate might be 30 frames persecond. Accordingly, 30 times per second, the audio rendering objectissues what is known as an invalidation call to whatever object ishosting it. The invalidation call essentially notifies the host that itis to call the audio rendering object with a Draw or Paint commandinstructing the rendering object 608 to render whatever visualization isto be rendered in the unified rendering area 406. When the audiorendering object 608 receives the Draw or Paint command, it then takessteps to ascertain the preprocessed data that is associated with thecurrently playing audio sample. Once the audio rendering object hasascertained this preprocessed data, it can issue a call to theappropriate effect, say for example, the dot plane effect, and providethis preprocessed data to the dot plane effect in the form of aparameter that can then be used to render the visualization.

As a specific example of how this can take place, consider thefollowing. When the audio rendering object receives its Draw or Paintcall, it calls the audio sample preprocessor 804 to query thepreprocessor for data, i.e. frequency data or waveform data associatedwith the currently playing audio sample. To ascertain what data itshould send the audio rendering object 608, the audio samplepreprocessor performs a couple of steps. First, it queries the renderer810 to ascertain the time that is associated with the audio sample thatis currently playing. Once the audio sample preprocessor ascertains thistime, it searches through the various data structures associated witheach of the audio samples to find the data structure with the timestampnearest the time associated with the currently-playing audio sample.Having located the appropriate data structure, the audio samplepreprocessor 804 provides the frequency data and any other data thatmight be needed to render a visualization to the audio rendering object608. The audio rendering object then calls the appropriate effect withthe frequency data and an area to which it should render (i.e. theunified rendering area 406) and instructs the effect to render in thisarea. The effect then takes the data that it is provided, incorporatesthe data into the effect that it is going to render, and renders theappropriate visualization in the given rendering area.

Exemplary Visualization Methods

FIG. 10 is a flow diagram that describes steps in a method in accordancewith one embodiment. The method can be implemented in any suitablehardware, software, firmware or combination thereof In the illustratedand described embodiment, the method is implemented in software. Oneexemplary software system that is capable of implementing the methodabout to be described is shown and described with respect to FIG. 8. Itis to be appreciated and understood that FIG. 8 constitutes but oneexemplary software system that can be utilized to implement the methodabout to be described.

Step 1000 receives multiple audio samples. These samples are typicallyreceived into an audio sample pipeline that is configured to provide thesamples to a renderer that renders the audio samples so a user canlisten to them. Step 1002 preprocesses the audio samples to providecharacterizing data for each sample. Any suitable characterizing datacan be provided. One desirable feature of the characterizing data isthat it provides some measure from which a visualization can berendered. In the above example, this measure was provided in the form offrequency data or wave data. The frequency data was specifically derivedusing a Fast Fourier Transform. It should be appreciated and understoodthat characterizing data other than that which is considered “frequencydata”, or that which is specifically derived using a Fast FourierTransform, can be utilized. Step 1004 determines when an audio sample isbeing rendered. This step can be implemented in any suitable way. In theabove example, the audio renderer is called to ascertain the timeassociated with the currently-playing sample. This step can beimplemented in other ways as well. For example, the audio renderer canperiodically or continuously make appropriate calls to notify interestedobjects of the time associated with the currently-playing sample. Step1006 then uses the rendered audio sample's characterizing data toprovide a visualization. This step is executed in a manner such that itis perceived by the user as occurring simultaneously with the audiorendering that is taking place. This step can be implemented in anysuitable way. In the above example, each audio sample's timestamp isused as an index of sorts. The characterizing data for each audio sampleis accessed by ascertaining a time associated with the currently-playingaudio sample, and then using the current time as an index into acollection of data structures. Each data structure containscharacterizing data for a particular audio sample. Upon finding a datastructure with a matching (or comparatively close) timestamp, thecharacterizing data for the associated data structure can then be usedprovide a rendered visualization.

It is to be appreciated that other indexing schemes can be utilized toensure that the appropriate characterizing data is used to render avisualization when its associated audio sample is being rendered.

FIG. 11 is a flow diagram that describes steps in a method in accordancewith one embodiment. The method can be implemented in any suitablehardware, software, firmware or combination thereof. In the illustratedand described embodiment, the method is implemented in software. Inparticular, the method about to be described is implemented by thesystem of FIG. 8. To assist the reader, the method has been broken intotwo portions to include steps that are implemented by audio renderingobject 608 and steps that are implemented by audio sample preprocessor804.

Step 1100 issues an invalidation call as described above. Responsive toissuing the invalidation call, step 1102 receives a Paint or Draw callfrom what ever object is hosting the audio rendering object. Step 1104then calls, responsive to receiving the Paint or Draw call, the audiosample preprocessor and queries the preprocessor for data characterizingthe audio sample that is currently being played. Step 1106 receives thecall from the audio rendering object and responsive thereto, queries theaudio renders for a time associated with the currently playing audiosample. The audio sample preprocessor then receives the current time andstep 1108 searches various data structures associated with the audiosamples to find a data structure with an associated timestamp. In theillustrated and described embodiment, this step looks for a datastructure having timestamp nearest the time associated with thecurrently-playing audio sample. Once a data structure is found, step1110 calls the audio rendering object with characterizing dataassociated with the corresponding audio sample's data structure. Recallthat the data structure can also maintain this characterizing data. Step1112 receives the call from the audio sample preprocessor. This callincludes, as parameters, the characterizing data for the associatedaudio sample. Step 1114 then calls an associated effect and provides thecharacterizing data to the effect for rendering. Once the effect has theassociated characterizing data, it can render the associatedvisualization.

This process is repeated multiple times per second at an associatedframe rate. The result is that a visualization is rendered andsynchronized with the audio samples that are currently being played.

Throttling

There are instances when visualizations can become computationallyexpensive to render. Specifically, generating individual frames of somevisualizations at a defined frame rate can take more processor cyclesthan is desirable. This can have adverse effects on the media playerapplication that is executing (as well as other applications) becauseless processor cycles are left over for it (them) to accomplish othertasks. Accordingly, in one embodiment, the media player application isconfigured to monitor the visualization process and adjust the renderingprocess if it appears that the rendering process is taking too muchtime.

FIG. 12 is a flow diagram that describes a visualization monitoringprocess in accordance with one embodiment. The method can be implementedin any suitable hardware, software, firmware or combination thereof. Inthe illustrated example, the method is implemented in software. Oneembodiment of such software can be a media player application that isexecuting on a client computer.

Step 1200 defines a frame rate at which a visualization is to berendered. This step can be accomplished as an inherent feature of themedia player application. Alternately, the frame rate can be set in someother way. For example, a software designer who designs an effect forrendering a visualization can define the frame rate at which thevisualization is to be rendered. Step 1202 sets a threshold associatedwith the amount of time that is to be spent rendering a visualizationframe. This threshold can be set by the software. As an example,consider the following. Assume that step 1200 defines a target framerate of 30 frames per second. Assume also that step 1202 sets athreshold such that for each visualization frame, only 60% of the timecan be spent in the rendering process. For purposes of this discussionand in view of the FIG. 8 example, the rendering process can beconsidered as starting when, for example, an effect receives a call fromthe audio rendering object 608 to render its visualization, and endingwhen the effect returns to the audio rendering object that it hascompleted its task. Thus, for each second that a frame can be rendered,only 600 ms can actually be spent in the rendering process.

FIG. 13 diagrammatically represents a timeline in one-second increments.For each second, a corresponding threshold has been set and is indicatedby the cross-hatching. Thus, for each second, only 60% of the second canbe spent in the visualization rendering process. In this example, thethreshold corresponds to 600 ms of time.

Referring now to both FIGS. 12 and 13, step 1204 monitors the timeassociated with rendering individual visualization frames. This isdiagrammatically represented by the “frame rendering times” that appearabove the cross-hatched thresholds in FIG. 13. Notice that for the firstframe, a little more than half of the allotted time has been used in therendering process. For the second frame, a little less than half of thetime has been used in the rendering process. For all of the illustratedframes, the rendering process has occurred within the defined threshold.The monitored rendering times can be maintained in an array for furtheranalysis.

Step 1206 determines whether any of the visualization rendering timesexceed the threshold that has been set. If none of the rendering timeshas exceeded the defined threshold, then step 1208 continues renderingthe visualization frames at the defined frame rate. In the FIG. 13example, since all of the frame rendering times do not exceed thedefined threshold, step 1208 would continue to render the visualizationat the defined rate.

Consider now FIG. 14. There, the rendering time associated with thefirst frame has run over the threshold but is still within theone-second time frame. The rendering time for the second frame, however,has taken not only the threshold time and the remainder of theone-second interval, but has extended into the one-second intervalallotted for the next frame. Thus, when the effect receives a call torender the third frame of the visualization, it will still be in theprocess of rendering the second frame so that it is quite likely thatthe third frame of the visualization will not render properly. Noticealso that had the effect been properly called to render the third frame(i.e. had there been no overlap with the second frame), its renderingtime would have extended into the time allotted for the next-in-lineframe to render. This situation can be problematic to say the least.

Referring again to FIG. 12, if step 1206 determines that the thresholdhas been exceeded, then step 1210 modifies the frame rate to provide aneffective frame rate for rendering the visualization. In the illustratedand described embodiment, this step is accomplished by adjusting theinterval at which the effect is called to render the visualization.

Consider, for example, FIG. 15. There, an initial call interval isrepresented below the illustrated time line. When the second frame isrendered, the rendering process takes too long. Thus, as noted above,step 1210 modifies the frame rate by adjusting the time (i.e.lengthening the time) between calls to the effect. Accordingly, an“adjusted call interval” is indicated directly beneath the initial callinterval. Notice that the adjusted call interval is longer than theinitial call interval. This helps to ensure that the effects get calledwhen they are ready to render a visualization and not when they are inthe middle of rendering a visualization frame.

Notice also that step 1210 can branch back to step 1204 and continuemonitoring the rendering times associated with the individualvisualization frames. If the rendering times associated with theindividual frames begin to fall back within the set threshold, then themethod can readjust the call interval to the originally defined callinterval.

Conclusion

The above-described methods and systems overcome problems associatedwith past media players in a couple of different ways. First, the userexperience is enhanced through the use of a unified rendering area inwhich multiple different media types can be rendered. Desirably allmedia types that are capable of being rendered by a media player can berendered in this rendering area. This presents the various media in aunified, integrated and organized way. Second, visualizations can beprovided that more closely follow the audio content with which theyshould be desirably synchronized. This not only enhances the userexperience, but adds value for third party visualization developers whocan now develop more accurate visualizations.

Although the invention has been described in language specific tostructural features and/or methodological steps, it is to be understoodthat the invention defined in the appended claims is not necessarilylimited to the specific features or steps described. Rather, thespecific features and steps are disclosed as preferred forms ofimplementing the claimed invention.

1. A media player comprising software code that is configured to:provide a base rendering object associated with a rendering area inwhich multiple different media types can be rendered, the rendering areaproviding at least a portion of a media player user interface that canbe viewed by a user; provide multiple different media type renderingobjects each of which being associated with a different media type thatcan be rendered in the rendering area, the different media typerendering objects being configured to render their associated media andsharing common properties; receive media associated with a media typefor rendering in the rendering area; call the base rendering object withthe media type associated with the received media; ascertain, with thebase rendering object, an associated media type rendering object that isconfigured to render that media type; call the associated media typerendering object with the base rendering object; instruct the associatedmedia type rendering object to render the received media in therendering area; and render the associated media in the rendering areawith the media type rendering object.
 2. The media player of claim 1,wherein the different media types can comprises one or more of: audiotypes, video types, animation types, skin types, and HTML types.